Overview: Timestamp Range Merge
Use this operation to merge two datasets, typically one dataset of batch information, and one time series dataset. This results in an operation useful for investigating when time series data was used in the creation of a timeless article, such as a batch product, or a discrete product.
Only values from the time series dataset that fall within the defined timestamp range of the batch dataset will be included in the resulting dataset.
Properties
Category: |
Combine |
Performance risk: |
Moderate performance risk. The performance is influenced by the size of the text file being imported, which is determined by number of rows and/or the number of columns of the dataset. |
Knowledge required: |
Working knowledge of the software. |
Effect on datasets
How many datasets are required to perform this operation? |
Two |
Does it create a new dataset? |
Yes |
Can you reconfigure this operation? |
Yes |
Can you apply this operation to a locked dataset? |
Yes |
Does it modify the current dataset in any way? |
No |
Requirements
-
Two datasets: A batch definitions dataset and a data samples dataset
-
Batch definitions dataset:
-
-
This dataset, used to define the timestamp range, needs the following fields as a minimum:
-
Field |
Data type |
Batch identifying field or value field |
String, double or integer |
Batch start time field |
Date/Time |
Batch end time field |
Date/Time |
-
Data samples dataset:
-
-
This will typically come from a Historian.
-
The values will typically be time series values.
-
This dataset needs at least the following fields as a minimum:
-
Field |
Data type |
Value field |
String, double or integer |
Timestamp field |
Date/Time |
Comments
-
Batches can be of variable durations. This has no adverse effect when merging timestamp ranges. Note that only data from the time series dataset that fits into the selected timestamp range of the batch data will be included.
-
There can be time periods between the subsequent batches of any duration. This has no adverse effect when merging timestamp ranges. Again, note that only data from the time series dataset that fits into the timestamp range of the batch data will be included.
-
Timestamp range start and end times must be sequential: start times must be before end times.
-
If timestamp ranges overlap, be aware that the resulting dataset might contain duplicate timestamps or not be in chronological order.
-
Data quality:
-
Null values in the time series data will be included in the merged dataset.
-
Null values in the batch definitions dataset start or end time will cause the batch to be ignored.
-
Results
-
A new dataset is created. This contains at the minimum the batch identifying field, together with the time series timestamp fields and values from the data samples dataset where the timestamp series overlap with the timestamp range defined from the batch definitions dataset.
-
The new dataset will only contain the fields you selected from each of the original datasets.
-
The timestamp range fields are not included; they are simply used to define the timestamp range for merging.
Related topics: